Systems and methods for providing a dashboard for a collaboration work management platform

ABSTRACT

Systems, methods, and storage media for providing a dashboard for a collaboration work management platform are disclosed. Exemplary implementations may: manage environment state information for maintaining a collaboration environment; obtain a first set of units of work where a first user is associated with first units of work within the first set but not assigned to the first units of work; and/or effectuate presentation of a dashboard displaying work information for the first units of work within the first set and indicating titles for the first units of work within the first set, statuses of the first units of work within the first set, and user information for the one or more other users assigned to the first units of work within the first set.

FIELD OF THE DISCLOSURE

The present disclosure relates to systems and methods for providing adashboard for a collaboration work management platform.

BACKGROUND

Typical work management platforms present tasks or to-do items to theuser that is to perform the tasks or to-do items. Often, higher levelmanagement has difficulty obtaining a snapshot or overview of theprojects or tasks they manage that other users perform.

Data related to managers is typically limited to employee feedback orreview, and overall work product success. Data representing how managersactually manage and/or interact with the employees that work for themand/or the projects they are working has historically been unavailable.

SUMMARY

Managers and/or higher level employees that oversee and manage the workbeing performed by other users are often associated with severalprojects and/or tasks at a high level. These managers and higher levelemployees may ultimately be responsible for ensuring the projects andtasks are completed on schedule, but often struggle to do so because ofthe existing methods and graphical user interfaces for presenting workrelated information to users. The present disclosure relates to animproved user interface comprising a dashboard for displayingspecialized work information for units of work (e.g., projects, tasks,portfolios, and/or other units of work) a given user is associated with(e.g., managing and/or overseeing) but not assigned to (e.g., notactually performing the activities and/or actions for the units ofwork). The improved graphical user interface also enables userinteractions and behaviors that previously were not tracked on amanagerial/overseer's level, to be tracked and analyzed to determinemetrics and provide insight into how employees manage and oversee work.

One aspect of the present disclosure relates to a system configured toprovide a dashboard for a collaboration work management platform. Thesystem may include one or more hardware processors configured bymachine-readable instructions. The processor(s) may be configured tomanage environment state information for maintaining a collaborationenvironment. The environment state information may include user records,work unit records, and/or other records. The environment stateinformation may define a state of the collaboration environmentincluding user states, a work unit state, and/or other states. The userstates may be defined by the user records that define values of userparameters associated with users interacting with and viewing thecollaboration environment. The work unit states may be defined by thework unit records that define values of work unit parameters for unitsof work managed, created, and/or assigned within the collaborationenvironment.

The work unit records may define the values of the work unit parametersfor individual units of work within sets of units of work. A user may beassociated with the individual units of work within a given set. Beingassociated with the individual units of work within a given set mayindicate the user has a higher level of responsibility for theindividual units of work within the given set than other users that areassigned to the units of work. The one or more other users that areassigned to the units of work may be responsible for performing theactivities and/or actions for the units of work. The one or moreprocessor(s) may be configured to obtain a first set of units of workwhere a first user is associated with first units of work within thefirst set. The first user may be not assigned to the first units ofwork, but may be associated with the first units of work. One or moreother users may be assigned to the first units of work.

The processor(s) may be configured to effectuate presentation of adashboard displaying work information for the first units of work withinthe first set. A dashboard presented to a given user may include workinformation for units of work the given user is associated with. Thedashboard presented to the given user may include work information ofunits of work that other users, rather than the given user, are assignedto. The work information may be based on the work unit records andindicate titles for the first units of work within the first set,statuses of the first units of work within the first set, userinformation for the one or more other users assigned to the first unitsof work within the first set, and/or other information.

In some implementations, a system configured to provide a dashboard fora collaboration work management platform may include one or more of: oneor more servers, one or more client computing platforms, and/or othercomponents. The one or more servers may be configured to communicatewith one or more client computing platforms according to a client/serverarchitecture and/or other architecture. The one or more servers and/orclient computing platforms may include one or more physical processorsconfigured to execute one or more computer program components. Thecomputer program components may include one or more of an environmentstate component, a work unit component, a dashboard component, apresentation component, a notification component, and/or othercomponents.

The environment state component may be configured to manage environmentstate information for maintaining a collaboration environment. Theenvironment state information may include user records, work unitrecords, and/or other records. The environment state information maydefine a state of the collaboration environment including user states,work unit states, and/or other states. The user states may be defined bythe user records. The user records may define values of user parametersassociated with users interacting with and viewing the collaborationenvironment. The work unit states may be defined by the work unitrecords that define values of work unit parameters for units of workmanaged, created, and/or assigned within the collaboration environment.

The work unit records may define the values of the work unit parametersfor individual units of work within sets of units of work. The sets ofunits of work may include individual units of work that are associatedwith individual users. A user may be associated with the individualunits of work within a given set such that the user has a higher levelof responsibility for the individual units of work within the given setthan other users that are assigned to the units of work. The other usersthat are assigned to the units of work may be responsible for performingthe activities and/or actions for completing the units of work. Thegiven user may be responsible for managing, monitoring, and/or ensuringoverall progress of the individual units of work within the given set.

In some implementations, the work unit records may define values of thework unit parameters for individual subunits of work that correspond tothe individual units of work within a given set. The individual ones ofthe first units of work within the first set may have correspondingfirst subunits of work. The first user may not be assigned to the firstsubunits of work but one or more other users may be assigned to thefirst subunits of work.

The work unit component may be configured to obtain a first set of unitsof work. The first set of units of work may include first units of workwithin the first set. The first user may be associated with the firstunits of work within the first set. The first user may not be assignedto the first units of work within the first set, but one or more otherusers may be assigned to the first units of work within the first set.In some implementations, obtaining the first set of units of work mayinclude determining the first units of work that are associated with thefirst user to be included in the first set based on the user records,the work unit records, and/or other records.

In some implementations, the work unit component may be configured toobtain a second set of units of work were first user is associated withsecond units of work within the second set. The first user may not beassigned to the second units of work, but one or more other users may beassigned to the second units of work.

The presentation component may be configured to effectuate presentationof a dashboard displaying work information for the first units of workwithin the first set. The work information displayed via the dashboardfor the first set of units of work may include and/or indicate titlesfor the first units of work within the first set, statuses of the firstunits of work within the first set, user information for the one or moreother users assigned to the first units of work within the first set,due date information for the first units of work, start date informationfor the first units of work, priority information for the first units ofwork, stage of the first units of work, and/or other information. Insome implementations, the statuses of the first units of work may beindicated via colored status indicators within the dashboard (e.g.,green—on track, yellow—at risk, red—off track, etc.).

In some implementations, presentation of a second dashboard displayingwork information for the second units of work within the second set maybe effectuated. The second dashboard may display work information forthe second units of work within the second set. The work information maybe based on the work unit records. The work information for the secondunits of work may indicate titles for the second units of work, statusesof the second units of work within the second set, user information forthe one or more other users assigned to the second units of work, duedate information for the second units of work, start date informationfor the second units of work, priority information for the second unitsof work, stage of the second units of work, and/or other information.

In some implementations, the dashboard may include one or more drop-downbuttons corresponding to individual ones of the first units of workwithin the first set. Responsive to a user selecting a drop-down buttoncorresponding to a first unit of work, the work information for firstsubunits of work corresponding to the first unit of work may bepresented. The work information for the first subunits of work mayinclude title for the first subunits of work, statuses of the firstsubunits of work, user information for the one or more other usersassigned to the first subunits the work, due date information for thefirst subunits of work, and/or other information.

In some implementations, the dashboard may include contact buttonscorresponding to individual ones of the units of work and/or individualones of the corresponding subunits of work. The contact buttons may beused to initiate a notification reminding the one or more other usersassigned to the units of work and/or the corresponding subunits of workto provide a reminder and/or request a status update related to theunits of work and/or the corresponding subunits of work.

The dashboard component may be configured to generate the dashboard fordisplaying the work information for the first units of work within thefirst set. In some implementations, the dashboard component may beconfigured to monitor interactions of the first user with the firstunits of work. Dashboard component may be configured to determine one ormore metrics characterizing the interactions of the first user with thefirst units of work. The one or more metrics may include a quantity offollow-ups, a follow-up frequency, a time period between follow-ups,follow-up timing, which users receive follow-ups, a quantity of views,viewing frequency, and/or other metrics characterizing follow-ups and/orother interactions of the first user with the first units of work.

Notification component may be configured to generate a firstnotification for the first unit of work responsive to a user selecting afirst contact button corresponding to the first unit of work. The firstnotification may include a reminder and/or status update request for thefirst unit of work. The first notification may be from and/or indicatedas being from the user that selected the first contact button (e.g., thefirst user).

These and other features, and characteristics of the present technology,as well as the methods of operation and functions of the relatedelements of structure and the combination of parts and economies ofmanufacture, will become more apparent upon consideration of thefollowing description and the appended claims with reference to theaccompanying drawings, all of which form a part of this specification,wherein like reference numerals designate corresponding parts in thevarious figures. It is to be expressly understood, however, that thedrawings are for the purpose of illustration and description only andare not intended as a definition of the limits of the invention. As usedin the specification and in the claims, the singular form of “a”, “an”,and “the” include plural referents unless the context clearly dictatesotherwise.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a system configured to provide a dashboard for acollaboration work management platform, in accordance with one or moreimplementations.

FIG. 2A illustrates a dashboard for a collaboration work managementplatform, in accordance with one or more implementations.

FIG. 2B illustrates a dashboard for a collaboration work managementplatform, in accordance with one or more implementations.

FIG. 3 illustrates a notification within a dashboard for a collaborationwork management platform, in accordance with one or moreimplementations.

FIG. 4 illustrates a transmitted notification, in accordance with one ormore implementations.

FIG. 5 illustrates a flow chart of a method for providing a dashboardfor a collaboration work management platform, in accordance with one ormore implementations.

DETAILED DESCRIPTION

FIG. 1 illustrates a system 100 configured to provide a dashboard for acollaboration work management platform, in accordance with one or moreimplementations. In some implementations, system 100 may include one ormore servers 102. Server(s) 102 may be configured to communicate withone or more client computing platforms 104 according to a client/serverarchitecture and/or other architectures. Client computing platform(s)104 may be configured to communicate with other client computingplatforms via server(s) 102 and/or according to a peer-to-peerarchitecture and/or other architectures. Users may access system 100 viaclient computing platform(s) 104.

Server(s) 102 may be configured by machine-readable instructions 106.Machine-readable instructions 106 may include one or more instructioncomponents. The instruction components may include computer programcomponents. The instruction components may include one or more of anenvironment state component 108, a work unit component 110, apresentation component 114, a notification component 116, and/or otherinstruction components.

As is illustrated in FIG. 1 , system 100 may include one or more of: oneor more servers 102, one or more client computing platforms 124,external resources 122, and/or other components for providing adashboard representing workflow for a collaboration work managementplatform. Users may interact with system 100 via one or more clientcomputing platforms 124. The one or more servers 102 may be configuredto communicate with one or more client computing platforms 124 accordingto a client/server architecture and/or other communication schemes. Theone or more client computing platforms 124 may include one or more of acellular telephone, a smartphone, a digital camera, a laptop, a tabletcomputer, a desktop computer, a television set-top box, smart TV, agaming console, and/or other client computing platforms.

Environment state component 108 may be configured to manage environmentstate information for maintaining a collaboration environment. By way ofnon-limiting example, the work unit states may be defined by the workunit records that define values of work unit parameters for units ofwork managed, created, and/or assigned within the collaborationenvironment. In some implementations, the work unit state may include aproject state, a task state, a sub-tasks state, and/or other states. Thework unit records may include project records, task records, sub-taskrecords, and/or other records.

The environment state information may include user records and work unitrecords. The environment state information may define a state of thecollaboration environment including user states and work unit states.The user states may be defined by the user records that define values ofuser parameters associated with users interacting with and viewing thecollaboration environment. The user parameters associated with the usersinteracting with and/or viewing the collaboration environment mayinclude parameters describing the users, their actions within thecollaboration environment, their settings, and/or other userinformation; and/or metadata associated with the users, their actionswithin the environment, their settings, and/or other user information.Individual ones of the users may be associated with individual ones ofthe user records. A user record may define values of the user parametersassociated with a given user interacting with and/or viewing thecollaboration environment.

The user parameters may, by way of non-limiting example, include one ormore of: a user name, a user role, a user department, descriptive usercontent, a to-email, a from-email, a photo, an organization, aworkspace, one or more projects (which may include project parametersdefined by one or more work unit records); one or more items of work(which may include one or more work item parameters defined by one ormore work item records), one or more user comments, one or more teamsthe user belongs to, one or more of the user display settings (e.g.,colors, size, project order, task order, other work unit order, etc.),one or more authorized applications, one or more presence/interactionparameters (e.g., indicating presence and/or interaction level at anenvironment level, work unit level, project level, task all, applicationlevel, etc.), one or more notification settings, one or more progressparameters, status information for one or more work units the user isassociated with, one or more statistics related to a given user (e.g.,how many units of work the user has completed, how quickly the usercompleted the units of work, how quickly the user completes certaintypes of work units, the efficiency of the user, bandwidth of the user,activity level of the user, etc.), application access information (e.g.,username/password for one or more third-party applications), one or morefavorites and/or priorities, other user parameters for the given user,and/or other user parameters and/or work unit parameters, for one ormore work units the given user is associated with.

The work unit parameters for work units managed created, and/or assignedwithin the collaboration environment may include parameters describingone or more work units managed, created, and/or assigned within thecollaboration environment and/or via the collaboration work managementplatform, and/or the metadata associated with the one or more workunits. Individual ones of the work units may be associated withindividual ones of the work unit records. A work unit record may definevalues of the work unit parameters associated with a given work unitmanaged, created, and/or assigned within the collaboration environmentand/or via the collaboration work management platform. A given work unitmay have one or more owners and/or one or more team members working onthe given work unit. Work units may include one or more to-do items,action items, objectives, and/or other units of work one or more usersshould and/or plan on accomplishing. Units of work may be created by agiven user for the given user and/or created by the given user andassigned to one or more other users. A given work unit may include oneor more projects, tasks, sub-tasks, portfolios (e.g., a grouping or setof work units), and/or other units of work assigned to and/or associatedwith one or more users.

The work unit parameters may, by way of non-limiting example, includeone or more of: one or more units of work, one or more user commentparameters (e.g., a creator, a recipient, one or more followers, one ormore other interested parties, content, one or more times, upvotes,other hard-coded responses, etc.), a work unit name, a work unitdescription, one or more work unit dates (e.g., a start date, a duedate, a completion date, and/or other work unit dates), one or moremembers associated with a unit of work (e.g., an owner, one or moreother project/task members, member access information, and/or other workunit members and/or member information), a status and/or progress (e.g.,an update, a hardcoded status update, a measured status, quantity ofwork units remaining in a given project, completed work units in a givenproject, and/or other status parameter), one or more attachments,notification settings, privacy, an associated URL, one or moreinteraction parameters (e.g., sources of the interactions, context ofthe interactions, content of the interactions, time for theinteractions, and/or other interaction parameters), updates, ordering ofunits of work within a given unit of work (e.g., tasks within a project,sub-tasks within a task, etc.,), state of a workspace for a given unitof work (e.g., application state parameters, application status,application interactions, user information, and/or other parametersrelated to the state of the workspace for a unit of work), dependenciesbetween one or more work units, one or more custom fields (e.g.,priority, cost, stages, and/or other custom fields), other work unitparameters for the given work units, and/or other work unit parameters,and/or user parameters for one or more users and/or work units the givenproject is associated with.

It is noted that any metadata and/or values of parameters related to anyusers, units of work, projects, tasks, subtasks, portfolios (e.g., agrouping or set of work units), and/or other units of work may beconsidered values of user parameters and/or work unit parameters. Theterms “user parameters” and/or “work unit parameters” may be usedinterchangeably herein.

Work unit component 110 may be configured to obtain a first set of unitsof work. A first user may be associated with first units of work withinthe first set. A user may be associated with the individual units ofwork within the given set such that the user has a higher level ofresponsibility for the individual units of work within the given setthan other users that are assigned to the units of work and responsiblefor performing the activities and actions for the units of work. By wayof non-limiting example, a given user being associated with individualunits of work may indicate the given user manages the given units ofwork, is responsible for the individual units of work, and/or overseesother users performing the activities and/or actions for the individualunits of work. The individual units of work within a given set may beassociated and/or related to one another, and/or may have one or morecharacteristics in common. The individual units of work within a givenset may be associated with the given user, associated with the samedepartment, part of the same larger project, associated with the sameproduct or goal, associated with a set of users associated with thegiven user (e.g., a team or group of users overseen or managed by thegiven user), and/or otherwise associated with, related to, and/or havingone or more characteristics in common with one another. By way ofnon-limiting example, the individual units of work may include projects,tasks, portfolios (e.g., a grouping or set of work units), and/or otherunits of work.

The first set of units of work (e.g., a portfolio or multiple nestedportfolios represented via a given dashboard) may have metadataassociated with the first set of units of work (e.g., the portfolio).For example, one or more users (e.g., a team), date information (e.g., adue date or completion date for the first set of units of work), statusinformation (e.g., a status color) for the first set, a description forthe first set, and/or other metadata. The metadata may be automaticallydetermined and/or determined by a user based on the user records, thework unit records, user input, and/or other information

Obtaining the first set of units of work may include determining thefirst units of work that are associated with the first user to beincluded in the first set. Determining the first units of work to beincluded in the first set may be based on the user records and the workunit records. In some implementations, obtaining the first set of unitsof work may include receiving user input indicating the first units ofwork that are associated with the first user to be included in the firstset. In some implementations, obtaining the first set of units of workmay include receiving user input indicating selection of one or moreunits of work to include and/or add to the first set of units of work.Work unit component 110 may be configured to determine one or moresuggestions for units of work that should be included and/or added tothe first set of units of work. The one or more suggestions may bepresented to a user to facilitated user selection of the one or moresuggested units of work to include and/or add in the first set of unitsof work.

In some implementations, the individual ones of the first units of workwithin the first set may have corresponding first subunits of work.Responsive to the first units of work including projects, thecorresponding first subunits of work may include tasks within theindividual projects. In some implementations, the units of work mayinclude portfolios comprising multiple other units of work and/orsubunits of work. The portfolios may include a grouping or set of unitsof work and/or sub units of work associated with a given user (e.g., thefirst user, etc.).

The first user may not be assigned to the first subunits of work, butone or more other users may be assigned to the first subunits of work.By way of non-limiting example, a given user being associated withindividual subunits of work may indicate the given user manages thegiven subunits of work and/or the corresponding units of work, isresponsible for the individual subunits of work and/or the correspondingunits of work, and/or oversees other users performing the activitiesand/or actions for the individual subunits of work and/or thecorresponding units of work.

In some implementations, work unit component 110 may be configured toobtain a second set of units of work. The first user may be not assignedto the second units of work. One or more other users may be assigned tothe second units of work. The first user may own, manage, and/or overseethe second units of work within the second set. Obtaining the second setof units of work may include receiving user input indicating the secondunits of work that are associated with the first user to be included inthe second set.

In some implementations, dashboard component 112 may be configured togenerate one or more dashboards for individual users within thecollaboration work management platform. The one or more dashboards mayinclude a first dashboard displaying work information for the firstunits of work within the first set generated for the first user. By wayof non-limiting example, the first dashboard may include a list of thefirst units of work within the first set along with correspondingmetadata for the first units of work. The corresponding metadata for thefirst units of work may include at least some of the work informationfor the first units of work associated with the first user for which thefirst dashboard is generated.

The work information displayed via the dashboard may include userinformation for the one or more other users that are assigned to thefirst subunits of work and responsible for performing the activities andactions for the subunits of work. The dashboard may include contactbuttons corresponding to individual ones of the first units of work. Thedashboard may include one or more drop down buttons such that responsiveto the first user selecting a first drop down button corresponding to afirst unit of work, the work information for the first subunits of workcorresponding to the first units of work is presented. By way ofnon-limiting example, the work information for the first subunits ofwork may include titles for the first subunits of work, statuses of thefirst subunits of work, user information for the one or more other usersassigned to the first subunits of work, and/or due date information forthe first subunits of work. The dashboard may configurable such that auser may customize the dashboard view. For example, if the user wants toshare the dashboard with another user, the user may only want certaininformation (e.g., certain work information, status information, and/orother information) presented via the dashboard.

In some implementations, the dashboard may include one or more visualcharts and/or graphs based on the work information and/or metadataassociated with the one or more units of work within a set of units ofwork. By way of non-limiting example, individual units of work (e.g.,projects, tasks, and/or other units of work) may be included in a piechart illustrating status (e.g., red, yellow, green, and/or other statusindicators) of the units of work (e.g., projects, tasks, and/or otherunits of work) within a given set of units of work (e.g., a portfolioand/or other set of units of work).

Presentation component 114 may be configured to effectuate presentationof one or more dashboards for displaying work information for units ofwork within one or more sets of units of work associated with a givenuser. Presentation component 114 may be configured to effectuatepresentation of a dashboard displaying work information for the firstunits of work within the first set. The first dashboard may include alist of the first units of work within the first set and correspondingmetadata for the first units of work. The corresponding metadata mayinclude at least some of the work information for the first units ofwork. The work information displayed via the dashboard may indicatetitles for the units of work within the given set displayed via thedashboard, statuses of the units of work within the given set displayedvia the dashboard, user information for the one or more other usersassigned to the units of work within the given set displayed via thedashboard, due date information for the units of work within a given setdisplayed via the dashboard, and/or other work information. The workinformation may be based on the work unit records. By way ofnon-limiting example, the work information for the first units of workincluded in the first dashboard may indicate titles for the first unitsof work within the first set, statuses of the first units of work withinthe first set, user information for the one or more other users assignedto the first units of work within the first set, due date informationfor the first units of work, and/or other information for the firstunits of work.

In some implementations, dashboard component 112 may be configured toeffectuate presentation of a second dashboard displaying workinformation for second units of work within a second set. The workinformation may indicate titles for the second units of work within thesecond set, statuses of the second units of work within the second set,user information for the one or more other users assigned to the secondunits of work within the second set, due date information for the secondunits of work within the second set, start date information for thesecond units of work within the second set, priority information for thesecond units of work, stage of the second units of work, and/or otherinformation and/or other information for the second units work with andthe second set.

In some implementations, the statuses of the units of work may beindicated via colored status indicators, shape indicators, and/or otherindicators within the dashboard. By way of non-limiting example, thecolored status indicators may include a red indicator indicating thecorresponding unit of work is off-track and/or behind schedule, a yellowindicator indicating the corresponding unit of work is at risk of beingoff-track and/or behind schedule, a green indicator indicating thecorresponding unit of work is on track and/or on schedule, and/or othercolored indicators.

The work information displayed via the dashboard may include userinformation for the one or more other users that are assigned to thefirst units of work and/or the first subunits of work. The userinformation may include a user name, a department, a title, a location,an availability, and/or other user information for the one or more otherusers that are assigned to the first units of work and/or the firstsubunits of work. Users that are assigned to the first units of workand/or the first subunits of work may be responsible for performing theactivities and/or actions for completing the first units of work and/orthe first subunits of work. The dashboard may include contact buttonscorresponding to individual ones of the first units of work.

In some implementations, the dashboard may include one or more drop downbuttons corresponding to individual ones of the units of work. The oneor more drop down buttons may initiate display of work information forthe subunits of work corresponding to a given unit of work. For example,responsive to the first user selecting a first drop down buttoncorresponding to a first unit of work, the work information for thefirst subunits of work corresponding to the first units of work ispresented. By way of non-limiting example, the work information for thefirst subunits of work display responsive to selection of a drop downbutton may include titles for the first subunits of work, statuses ofthe first subunits of work, user information for the one or more otherusers assigned to the first subunits of work, due date information forthe first subunits of work, and/or other work information for the firstsubunits of work.

In some of limitations, the dashboard may include contact buttonscorresponding to individual ones of the units of work and/or subunits ofwork. The users may select individual contact buttons in order toinitiate a notification for the corresponding unit of work and/orsubunit of work. The contact buttons may include GUI buttons and/orother interface features that are selectable by the uses. By way ofnon-limiting example, the first user may select a first contact buttoncorresponding to a first unit of work within the first dashboard.

FIG. 2A illustrates a dashboard for a collaboration work managementplatform, in accordance with one or more implementations. Dashboard 200may display work information 201 for units of work 204 within set 202.Work information 201 for units of work 204 within set 202 may bedisplayed in rows corresponding to individual ones of the units of work204. Dashboard 200 may display units of work 204 that are associatedwith User 1 206, but assigned to one or more other users indicated byuser information 214. Units of work 204 within set 202 may be related toand/or associated with one another. By way of non-limiting example,units of work 204 within set 202 may be projects related to productGrowth and Adoption.

Work information 201 displayed within dashboard 200 may include titlesfor units of work 204, statuses 206, due dates and/or start dates 208,stage information 210, priority information 212, user information 214,and/or other information for units of work associated with User 1 206within set 202. Dashboard 200 may include drop down buttons 205corresponding to individual ones of units of work 204. Dashboard 200Amay include contact buttons 216 corresponding to the units of work 204.

FIG. 2B illustrates a dashboard for a collaboration work managementplatform, in accordance with one or more implementations. Dashboard 200Bmay display work information 250 for one or more subunits of work 218(e.g., tasks 1-4) corresponding to unit of work 204F (e.g., Project 6).Work information 254 for subunits of work 218 may be presentedresponsive to a user (e.g., User 1 206) selecting drop down button 205F.Work information 254 for subunits of work 218 may be displayed in rowscorresponding to individual ones of the subunits of work 218.

Work information 250 displayed within dashboard 200 may include titlesfor subunits of work 218, statuses 220, due dates and/or start dates222, stage information 224, priority information 226, user information228, and/or other information for subunits of work 218 associated withUser 1 206 and/or corresponding to unit of work 204F (e.g., Project 6).Dashboard 200B may include contact buttons 230 corresponding to thesubunits of work 218.

Returning to FIG. 1 , notification component 116 may be configured togenerate, one or more notifications for individual units of work and/orsubunits of work. Notification component 116 may be configured togenerate a first notification for the first unit of work. The firstnotification may be generated responsive to the first user selecting afirst contact button corresponding to a first unit of work. Thenotification may include a reminder, custom message, and/or statusupdate request for the first unit of work from the first user. Thenotifications may be automatically generated, editable by the given userinitiating the notifications, and/or drafted by the given userinitiating the notifications. The one or more notifications initiatedvia the dashboard and or generated by notification component 116 may betransmitted to the one or more other users assigned to the correspondingunits of work and/or subunits of work. By way of non-limiting example,the first notification may include work information for the first unitof work may be presented in the first notification. The firstnotification may include a reminder and/or status update request for thefirst unit of work. Notification component may be configured to transmitthe first notification to a second user assigned to the first unit ofwork. The first notification may be from and/or indicated as being fromthe user that selected the first contact button (e.g., the first user).

In some implementations, when presented to the second user, the firstnotification may include one or more suggestions for responding to thefirst notification. For example, the first notification may include oneor more units of work (e.g., milestones and/or tasks) to update inresponse to the first notification.

In some implementations, a second contact button corresponding to afirst subunit of work may be presented to the first user responsive tothe first user initiating a drop down button corresponding to a firstunit of work. The first user may select the second contact button toinitiate generation of a second notification for the first subunit ofwork. The second notification may be generated and/or transmitted to athird user assigned to the first subunit of work.

FIG. 3 illustrates a notification within a dashboard for a collaborationwork management platform, in accordance with one or moreimplementations. Notification may be generated responsive to User 1 306selecting contact button 316. Notification 302 may include anautomatically generated notification message 303. User 1 306 may be ableto edit notification message 303 prior to sending to the user that isassigned to unit of work 304 (e.g., Project 1) as indicated by userinformation 314. Send button 305 may be selected by User 1 306 oncenotification message 303 is ready to be transmitted to the user assignedto unit of work 304 as indicated by user information 314.

FIG. 4 illustrates a transmitted notification, in accordance with one ormore implementations. Notification 402 for Project 1 may be transmittedto the user assigned to Project 1. Notification 402 may be from User 1and include the final notification message 404. User 410 may respond tonotification 402 by selecting reply button 406 and/or update button 408.Reply button 406 may initiate a new message window for drafting aresponse to notification 402. Update button 408 may trigger andautomatic update to be sent to User 1 based on recent progress, actions,and/or activities performed related to Project 1.

Returning to dashboard component 112, dashboard component 112 may beconfigured by machine readable instructions to monitor interactions ofthe first user with the first units of work and/or correspondingsubunits of work. Interactions of the given user with the given units ofwork and/or the given subunits of work may include views, clicks (e.g.,drop down menu selections, contact button selections, unit of workselections, subunit of work selections, and/or other selections and/oruser input/clicks received via the dashboard), follow-up initiationsand/or notifications sent and/or received, and/or other interactions.

Dashboard component 112 may be configured by machine readableinstructions to determine one or more metrics characterizing theinteractions of the given user (e.g., the user associated with the unitsof work presented via the given dashboard) with the units of work and/orsubunits of work displayed via the given dashboard. The one or moremetrics may include and/or indicate a quantity of follow-ups, afrequency of follow-ups, a time period between follow-ups, the timing offollow-ups, which users receive follow-ups, and/or other metricscharacterizing interactions of the given user with units of work and/orsubunits of work displayed within their dashboard. By way ofnon-limiting example, dashboard component 112 may be configured todetermine which days of the week and/or times of the day a given user ismost likely to initiate follow-ups; how frequently the given userinitiates follow-ups in total, on a work unit level, and/or on a set ofwork units level; how long the user waits before initiating anotherfollow-up after an initial follow-up for the same unit of work and/orsubunit of work. Dashboard component may be configured to determinewhich other users have received the more follow-ups and/or receivefollow-ups more often relative to one another.

In some implementations, server(s) 102, client computing platform(s)104, and/or external resources 118 may be operatively linked via one ormore electronic communication links. For example, such electroniccommunication links may be established, at least in part, via a networksuch as the Internet and/or other networks. It will be appreciated thatthis is not intended to be limiting, and that the scope of thisdisclosure includes implementations in which server(s) 102, clientcomputing platform(s) 104, and/or external resources 118 may beoperatively linked via some other communication media.

A given client computing platform 104 may include one or more processorsconfigured to execute computer program components. The computer programcomponents may be configured to enable an expert or user associated withthe given client computing platform 104 to interface with system 100and/or external resources 118, and/or provide other functionalityattributed herein to client computing platform(s) 104. By way ofnon-limiting example, the given client computing platform 104 mayinclude one or more of a desktop computer, a laptop computer, a handheldcomputer, a tablet computing platform, a NetBook, a Smartphone, a gamingconsole, and/or other computing platforms.

External resources 118 may include sources of information outside ofsystem 100, external entities participating with system 100, and/orother resources. In some implementations, some or all of thefunctionality attributed herein to external resources may be provided byresources included in system 100.

Server(s) 102 may include electronic storage 120, one or more processors122, and/or other components. Server(s) 102 may include communicationlines, or ports to enable the exchange of information with a networkand/or other computing platforms. Illustration of server(s) 102 in FIG.1 is not intended to be limiting. Server(s) 102 may include a pluralityof hardware, software, and/or firmware components operating together toprovide the functionality attributed herein to server(s) 102. Forexample, server(s) 102 may be implemented by a cloud of computingplatforms operating together as server(s) 102.

Electronic storage 120 may comprise non-transitory storage media thatelectronically stores information. The electronic storage media ofelectronic storage 120 may include one or both of system storage that isprovided integrally (i.e., substantially non-removable) with server(s)102 and/or removable storage that is removably connectable to server(s)102 via, for example, a port (e.g., a USB port, a firewire port, etc.)or a drive (e.g., a disk drive, etc.). Electronic storage 120 mayinclude one or more of optically readable storage media (e.g., opticaldisks, etc.), magnetically readable storage media (e.g., magnetic tape,magnetic hard drive, floppy drive, etc.), electrical charge-basedstorage media (e.g., EEPROM, RAM, etc.), solid-state storage media(e.g., flash drive, etc.), and/or other electronically readable storagemedia. Electronic storage 120 may include one or more virtual storageresources (e.g., cloud storage, a virtual private network, and/or othervirtual storage resources). Electronic storage 120 may store softwarealgorithms, information determined by processor(s) 122, informationreceived from server(s) 102, information received from client computingplatform(s) 104, and/or other information that enables server(s) 102 tofunction as described herein.

Processor(s) 122 may be configured to provide information processingcapabilities in server(s) 102. As such, processor(s) 122 may include oneor more of a digital processor, an analog processor, a digital circuitdesigned to process information, an analog circuit designed to processinformation, a state machine, and/or other mechanisms for electronicallyprocessing information. Although processor(s) 122 is shown in FIG. 1 asa single entity, this is for illustrative purposes only. In someimplementations, processor(s) 122 may include a plurality of processingunits. These processing units may be physically located within the samedevice, or processor(s) 122 may represent processing functionality of aplurality of devices operating in coordination. Processor(s) 122 may beconfigured to execute components 108, 110, 112, 114, and/or 116, and/orother components. Processor(s) 122 may be configured to executecomponents 108, 110, 112, 114, and/or 116, and/or other components bysoftware; hardware; firmware; some combination of software, hardware,and/or firmware; and/or other mechanisms for configuring processingcapabilities on processor(s) 122. As used herein, the term “component”may refer to any component or set of components that perform thefunctionality attributed to the component. This may include one or morephysical processors during execution of processor readable instructions,the processor readable instructions, circuitry, hardware, storage media,or any other components.

It should be appreciated that although components 108, 110, 112, 114,and/or are illustrated in FIG. 1 as being implemented within a singleprocessing unit, in implementations in which processor(s) 122 includesmultiple processing units, one or more of components 108, 110, 112, 114,and/or 116 may be implemented remotely from the other components. Thedescription of the functionality provided by the different components108, 110, 112, 114, and/or 116 described below is for illustrativepurposes, and is not intended to be limiting, as any of components 108,110, 112, 114, and/or 116 may provide more or less functionality than isdescribed. For example, one or more of components 108, 110, 112, 114,and/or 116 may be eliminated, and some or all of its functionality maybe provided by other ones of components 108, 110, 112, 114, and/or 116.As another example, processor(s) 122 may be configured to execute one ormore additional components that may perform some or all of thefunctionality attributed below to one of components 108, 110, 112, 114,and/or 116.

FIG. 5 illustrates a method 500 for aligning a three-dimensional modelof a surgical site, in accordance with one or more implementations. Theoperations of method 500 presented below are intended to beillustrative. In some implementations, method 500 may be accomplishedwith one or more additional operations not described, and/or without oneor more of the operations discussed. Additionally, the order in whichthe operations of method 500 are illustrated in FIG. 5 and describedbelow is not intended to be limiting.

In some implementations, method 500 may be implemented in one or moreprocessing devices (e.g., a digital processor, an analog processor, adigital circuit designed to process information, an analog circuitdesigned to process information, a state machine, and/or othermechanisms for electronically processing information). The one or moreprocessing devices may include one or more devices executing some or allof the operations of method 500 in response to instructions storedelectronically on an electronic storage medium. The one or moreprocessing devices may include one or more devices configured throughhardware, firmware, and/or software to be specifically designed forexecution of one or more of the operations of method 500.

An operation 502 may include managing environment state information formaintaining a collaboration environment. The environment stateinformation may include user records and work unit records. Theenvironment state information may define a state of the collaborationenvironment including user states and work unit states. Operation 502may be performed by one or more hardware processors configured bymachine-readable instructions including a component that is the same asor similar to environment state component 108, in accordance with one ormore implementations.

An operation 504 may include obtaining a first set of units of workwhere a first user is associated with first units of work within thefirst set. The first user may be not assigned to the first units of workbut one or more other users may be assigned to the first units of work.Operation 504 may be performed by one or more hardware processorsconfigured by machine-readable instructions including a component thatis the same as or similar to work unit component 110, in accordance withone or more implementations.

An operation 506 may include effectuating presentation of a dashboarddisplaying work information for the first units of work within the firstset. The work information may be based on the work unit records andindicate titles for the first units of work within the first set,statuses of the first units of work within the first set, and userinformation for the one or more other users assigned to the first unitsof work within the first set. Operation 506 may be performed by one ormore hardware processors configured by machine-readable instructionsincluding a component that is the same as or similar to presentationcomponent 114, in accordance with one or more implementations.

Although the present technology has been described in detail for thepurpose of illustration based on what is currently considered to be themost practical and preferred implementations, it is to be understoodthat such detail is solely for that purpose and that the technology isnot limited to the disclosed implementations, but, on the contrary, isintended to cover modifications and equivalent arrangements that arewithin the spirit and scope of the appended claims. For example, it isto be understood that the present technology contemplates that, to theextent possible, one or more features of any implementation can becombined with one or more features of any other implementation.

What is claimed is:
 1. A system configured to provide a dashboard withina collaboration environment, the system comprising: one or more physicalcomputer processors configured by machine-readable instructions to:manage environment state information for maintaining a collaborationenvironment, the environment state information including user recordsand work unit records, the user records describing users interactingwith or viewing the collaboration environment, the work unit recordsdescribing units of work managed within the collaboration environment,created within the collaboration environment, and assigned within thecollaboration environment, wherein one or more of the users areassociated with individual units of work and are described as having ahigher level of responsibility for the individual units of work thanother ones of the users that are assigned to the individual units ofwork, wherein the other ones of the users that are assigned to theindividual units of work are responsible for performing actions for theindividual units of work they are assigned to; identify a first set ofunits of work associated with a first user, wherein the first set ofunits of work is associated with the first user by virtue of the firstuser having the higher level of responsibility for the first set ofunits of work, wherein the first user is not assigned to the first setof units of work such that one or more of the other ones of the usersare assigned to the first set of units of work; and effectuatepresentation of a dashboard on a computing platform associated with thefirst user, the dashboard displaying work information for the first setof units of work associated with the first user, the work informationfor the first set of units of work describing the first set of units ofwork and the one or more of the other ones of the users that areassigned to the first set of units of work.
 2. The system of claim 1,wherein the one or more physical computer processors are furtherconfigured by the machine-readable instructions to: identify the firstuser; identify a second set of units of work, the first set of units ofwork comprising a subset of the second set of units of work; anddetermine which of the units of work within the second set of units ofwork the first user is associated with but not assigned to by virtue ofthe first user having the higher level of responsibility, such that thefirst set of units of work within the second set of units of work isdetermined to be associated with the first user by virtue of the firstuser having the higher level of responsibility for the first set ofunits of work and by virtue of the first user not being assigned to thefirst set of units of work.
 3. The system of claim 1, wherein the workinformation for the first set of units of work includes titles for thefirst set of units of work, statuses of the first set of units of work,and user information for the one or more of the other ones of the usersthat are assigned to the first set of units of work.
 4. The system ofclaim 1, wherein the dashboard includes contact buttons corresponding tothe individual units of work of the first set of units of work.
 5. Thesystem of claim 1, wherein the work unit records define individualsubunits of work that correspond to the individual units of work, suchthat the individual units of work of the first set of units of work havecorresponding ones of the individual subunits of work that the firstuser is not assigned to but the one or more of the other ones of theusers are assigned to.
 6. The system of claim 5, wherein the dashboardincludes one or more drop down buttons such that responsive to the firstuser selecting a first drop down button corresponding to a first unit ofwork, the work information for a first subunit of work corresponding tothe first unit of work is presented.
 7. The system of claim 3, whereinthe statuses of the first set of units of work are indicated via coloredstatus indicators within the dashboard.
 8. The system of claim 1,wherein determining the first set of units of work is associated withthe first user by virtue of the first user having the higher level ofresponsibility for the first set of units of work is based on the userrecords and the work unit records.
 9. The system of claim 1, wherein theone or more physical computer processors are further configured by themachine readable instructions to: monitor interactions of the first userwith the first set of units of work; and determine one or more metricscharacterizing the interactions of the first user with the first set ofunits of work, the one or more metrics including one or more of aquantity of follow-ups, a follow-up frequency, a time period betweenfollow-ups, follow-up timing, or which of the one or more of the otherones of the users receive follow-ups.
 10. The system of claim 1, whereinthe one or more physical computer processors are further configured bythe machine readable instructions to: effectuate presentation of asecond dashboard on the computing platform associated with the firstuser, the second dashboard displaying second work information for asecond set of units of work associated with the first user, wherein thesecond set of units of work is associated with the first user by virtueof the first user having the higher level of responsibility for thesecond set of units of work, wherein the first user is not assigned tothe second set of units of work such that one or more of the other onesof the users are assigned to the second set of units of work, the secondwork information for the second set of units of work describing thesecond set of units of work and the one or more of the other ones of theusers that are assigned to the second set of units of work.
 11. A methodto provide a dashboard within a collaboration environment, the methodcomprising: managing environment state information for maintaining acollaboration environment, the environment state information includinguser records and work unit records, the user records describing usersinteracting with or viewing the collaboration environment, the work unitrecords describing units of work managed within the collaborationenvironment, created within the collaboration environment, and assignedwithin the collaboration environment, wherein one or more of the usersare associated with individual units of work and are described as havinga higher level of responsibility for the individual units of work thanother ones of the users that are assigned to the individual units ofwork, wherein the other ones of the users that are assigned to theindividual units of work are responsible for performing actions for theindividual units of work they are assigned to; identifying a first setof units of work associated with a first user, wherein the first set ofunits of work is associated with the first user b virtue of the firstuser having the higher level of responsibility for the first set ofunits of work, wherein the first user is not assigned to the first setof units of work such that one or more of the other ones of the usersare assigned to the first set of units of work; and presenting adashboard on a computing platform associated with the first user, thedashboard displaying work information for the first set of units of workassociated with the first user, the work information for the first setof units of work describing the first set of units of work and the oneor more of the other ones of the users that are assigned to the firstset of units of work.
 12. The method of claim 11, further comprising:identifying the first user; identifying a second set of units of work,the first set of units of work comprising a subset of the second set ofunits of work; and determining which of the units of work within thesecond set of units of work the first user is associated with but notassigned to by virtue of the first user having the higher level ofresponsibility, including determining the first set of units of workwithin the second set of units of work is associated with the first userby virtue of the first user having the higher level of responsibilityfor the first set of units of work and by virtue of the first user notbeing assigned to the first set of units of work.
 13. The method ofclaim 11, wherein the work information for the first set of units ofwork includes titles for the first set of units of work, statuses of thefirst set of units of work, and user information for the one or more ofthe other ones of the users that are assigned to the first set of unitsof work.
 14. The method of claim 11, wherein the dashboard includescontact buttons corresponding to the individual units of work of thefirst set of units of work.
 15. The method of claim 11, wherein the workunit records define individual subunits of work that correspond to theindividual units of work, such that the individual units of work of thefirst set of units of work have corresponding ones of the individualsubunits of work that the first user is not assigned to but the one ormore of the other ones of the users are assigned to.
 16. The method ofclaim 15, wherein the dashboard includes one or more drop down buttonssuch that responsive to the first user selecting a first drop downbutton corresponding to a first unit of work, the work information for afirst subunit of work corresponding to the first unit of work ispresented.
 17. The method of claim 13, wherein the statuses of the firstset of units of work are indicated via colored status indicators withinthe dashboard.
 18. The method of claim 11, wherein determining the firstset of units of work is associated with the first user by virtue of thefirst user having the higher level of responsibility for the first setof units of work is based on the user records and the work unit records.19. The method of claim 11, further comprising: monitoring interactionsof the first user with the first set of units of work; and determiningone or more metrics characterizing the interactions of the first userwith the first set of units of work, the one or more metrics includingone or more of a quantity of follow-ups, a follow-up frequency, a timeperiod between follow-ups, follow-up timing, or which of the one or moreof the other ones of the users receive follow-ups.
 20. The method ofclaim 11, further comprising: presenting a second dashboard on thecomputing platform associated with the first user, the second dashboarddisplaying second work information for a second set of units of workassociated with the first user, wherein the second set of units of workis associated with the first user by virtue of the first user having thehigher level of responsibility for the second set of units of work,wherein the first user is not assigned to the second set of units ofwork such that one or more of the other ones of the users are assignedto the second set of units of work, the second work information for thesecond set of units of work describing the second set of units of workand the one or more of the other ones of the users that are assigned tothe second set of units of work.